Instant personal electronic parking system and method

ABSTRACT

A personal electronic parking system and method adapted to identify, track, predict, alert, manage and collect payment, and enforce on-street and off-street parking, the system including a central cloud network adapted to generate and manage user data and parking data, a user interface adapted to show users parking information relevant to the user, a unique machine-readable code, wherein the code provides identification of a specific vehicle used by the user, one or more sensors, one or more meter devices adapted to connect with the central cloud network and the user interface, and a parking payment and enforcement portal.

This application claims priority to U.S. Provisional Patent ApplicationNo. 63/076,564 filed Sep. 10, 2020, entitled “PERSONAL ELECTRONICPARKING METER DEVICE,” U.S. Provisional Patent Application No.63/131,357 filed Dec. 29, 2020, entitled “PERSONAL ELECTRONIC PARKINGMETER DEVICE,” and U.S. Provisional Patent Application No. 63/147,944filed Feb. 10, 2021, entitled “PERSONAL ELECTRONIC PARKING METERDEVICE,” which are hereby incorporated by reference herein.

The present invention relates to a personal parking system, moreparticularly, a method and system that handles parking related payments,parking enforcement, and predicts and recommends parking for its users.

BACKGROUND

The current state of the art provides drivers with disjointed apps,meter kiosks and street signs to locate available and permissibleparking spaces and to pay the parking fees. Drivers waste time and moneytrying to find available parking and to pay for parking fees, for bothon-street and off-street parking. Drivers can spend hours looking forand then paying for parking with the currently available parkingsystems.

SUMMARY OF THE INVENTION

The present invention provides an instant personal electronic parkingsystem (“iPEP™”) that gives a user the tools to efficiently locate andpay for on-street and off-street parking. Using the iPEP system, adriver can efficiently locate and quickly pay for both on-street andoff-street parking. The iPEP system also allows automaticidentification, tracking, predicting, managing, alerting, regulating andenforcing on-street and off-street parking from manually orautomatically entered data. The resulting data may be generated by oneor more cameras, microphones, crowdsourced data from community users, orsensors, (for example, RFIDS, proximity, or other physical sensors). TheiPEP system allows a user to input parking information into a userinterface such as a hardware device or application, and make, manage andtrack payments associated with parking vehicles, such as parking metersor tolls.

The present invention also provides parking enforcers, such asmunicipality regulators, the ability (remotely or through enforcementpersonnel) to issue violation notices, track and regulate violations,and collect fees for parking violations.

The present invention also provides automatic parking availabilitydetection using sensors such as cameras, audio, or proximity detectors.The parking availability is shared with the users on their userinterfaces via a cloud network, or on a local wireless network.

The present invention also provides a machine learning system that usesalgorithms to predict parking availability and recommend parking zonesbased on collected data including from crowdsourcing.

The present invention also provides the ability to share user data withthird party services to provide the user with coupons, discounts, orother incentives to share parking data.

The present invention provides a personal electronic parking systemadapted to identify, track, predict, alert, manage and collect payment,and enforce on-street and off-street parking, the system including acentral cloud network adapted to generate and manage user data andparking data, a user interface adapted to show users parking informationrelevant to the user, a unique machine-readable code, wherein the codeincludes identification of a specific vehicle used by the user, one ormore sensors, one or more meter devices adapted to connect with thecentral cloud network and the user interface, and a parking payment andenforcement portal.

The present invention also provides a method for managing and enforcingpersonal parking for on-street or off-street parking, the methodincluding the following steps: providing a personal parking payment andenforcement ability and providing with parking availability predictionsand recommendations.

The present invention also provides a machine learning system foron-street and off-street parking availability predictions andrecommendations, the system including a cloud network, at least onestorage unit, at least one sensor interface, a predictor model, arecommender model, and a classifier, wherein the classifier collects andextracts data for a parking predictor model and a recommender model.

DESCRIPTION OF THE DRAWINGS

Further objects, features, and advantages of the invention will becomeapparent from the following detailed description taken in conjunctionwith the accompanying figures showing illustrative embodiments of theinvention, in which:

FIG. 1 shows an exemplary embodiment of the elements included in theiPEP system;

FIGS. 2a and 2b show an exemplary embodiment of elements included in aniPEP hardware and firmware device (“iPEP-HD”);

FIG. 3 is a flow chart showing communication between multiple iPEPsystem user interfaces;

FIG. 4 is an exemplary flow chart for the automatic parking paymentprocess;

FIG. 5 is an exemplary flow chart of a parking enforcement and violationpayment collection process;

FIG. 6 shows a machine learning system for parking prediction andrecommendation; and

FIG. 7 shows an exemplary embodiment of crowdsourcing data collection.

DETAILED DESCRIPTION

The iPEP system allows drivers to use their user interfaces, forexample, mobile device, hardware device or a vehicle's on-boardinformation system, to find parking in a desired location, at a specifictime and for a particular duration. The iPEP system provides real-timeparking updates from other iPEP users; allows a user to pay for parking;and retains a log of all parking transactions in the user's account,viewable on the user's mobile device or the vehicle's on-boardinformation system, for example.

The iPEP system also allows municipalities to receive real time parkingviolation information, scan vehicle identification codes (e.g.,barcodes) to issue violation notices, enable system generated parkingviolation notices, enhance capabilities to collect fees for parkingviolations, and track parking patterns and violations.

A user must register and create a personal account to use and access theiPEP system. The user may create the account via website or mobileapplication, for example. Users can access their account on differentdevices and may sign out of their account and sign in at a later time.Users have access to a “Homepage” which displays information such as acurrent parking session, parking payment activity and history,notification settings, language choices, payment methods, and/or vehicleoptions. The user can register multiple vehicles on the same account.Vehicles can be added to an account by registering the vehicle andreceiving an associated machine-readable code, unique to the vehicle, oradding a pre-registered vehicle to the account.

The user interface receives, processes and displays available on-streetand off-street parking information in real-time. This may be a mobiledevice via a mobile app, a computer via a website, a vehicle's onboardinformation system such as Carplay via IOS or Android auto, or on aniPEP-HD.

iPEP system 1 provides the user with a map that displays parking-relatedinformation. The information shown is based on the user's currentlocation and time, or that of which the user manually inputs, forexample, parking at a different location and/or time. The map displaysavailable on-street parking in real time (free and/or metered); nearbyparking zone identification codes, for example, alphanumeric codes orbarcodes, available for on-street parking payment; available off-streetparking options and deals in real-time; parking alerts and reports; andnearby stores, restaurants and gas stations with available discounts andcoupons.

FIG. 1 shows an exemplary embodiment of iPEP system 1 components. System1 may include at least one processor 2, at least one storage unit 4,data input and display 6, wireless interface 8, wired interface 10,sensors 12, power source 16 and machine-readable code 18. Sensors 12 mayinclude a proximity sensor or antennae, RFID, camera 13, microphone 14and/or GPS 15. Data collected from sensors 12 is stored in one or moreexpandable internal storage memory 4. The data may be stored for one ormore days. Processor 2 performs computations on the stored or live datato extract different types of information. Data input and displayinterface 6 (user interface) may include a keyboard, touch screen,and/or voice input for data input. The user interface includes all userinteraction modalities such as a personal computer, mobile device, ahardware device, an onboard vehicle system, or any other suitabledevice, software, interactive modality or other mechanism able tointegrate, manipulate and/or operate the personal electronic parkingsystem and allow a user to input information. This includes typing on amobile device, voice input (e.g., Alexa interface), gesture interfaces(augmented or virtual reality), or brain-machine interfaces. The usercan use this to input data such as the parking zone identification codesand parking duration. This may be input manually or automaticallyselected. The entered data is collected and processed by computationalprocessor 2. The processed data is stored in internal storage memory 4.It is also displayed on a screen of interface 6 and can be mirrored onan external device for display. The entered data can be displayed in avariety of formats and languages. The data displayed may include thedate, parking zone identification code, parking location, parkingstatus, machine-readable code, remaining time, and/or other parkingrelated information, for example.

Raw data, processed data, extracted information, alerts, and other typesof output are transmitted to an iPEP-HD or an external user device via awireless 8 or wired interface 10, allowing the iPEP-HD display to mirrorwith a mobile device, for example, over at least one network interface.Wireless interface 8 may consist of a multitude of connections ofnetwork interfaces such as cellular, Wi-Fi, RFID, satellite, LTE, and 5Gencompassing local area network (LAN) and wide area network (WAN).

Machine-readable code 18 is unique for each vehicle. Machine-readablecode 18 encodes different types of information such as vehicleidentification, parking time usage status, and links to paymentgateways. Code 18 may be an analog or digital barcode or QR code, forexample. It can be affixed to a vehicle's windshield, such as a barcodesticker, or be part of the iPEP-HD. Code 18 can be scanned by otherdevices to extract the encoded information. Machine-readable code 18 maybe scanned by parking enforcers to access the vehicle's parkinginformation. Code 18 may include a lighting option that turns colorbased on a vehicle's parking status. For example, the code is colorlesswhile the vehicle is in motion, red when the user's parking session isunpaid or has expired, and/or green when a user's parking is paid andactive.

Street based/installed hardware devices with antennas (“meter devices”)3 enhance and ultimately replace the use of current parking metermachines. Meter devices 3 collect and transmit available parkinginformation and provide relevant information to municipalities andparking enforcement personnel. Meter devices 3 communicate wirelessly orvia wireline network with other similar devices or cloud servers,provides, or can perform functions of a parking meter machine. It can beused with currently installed parking meter machines and/or as astandalone apparatus. iPEP system 1 is accessible via meter device 3.Meter device 3 includes an antenna and may also include a camera 13 andaudio recording 14. Meter device 3 connects to parking software systemsboth off and online, whether the parking systems are used via a website,mobile application, car application, and/or iPEP-HD, for example.

Together with iPEP system 1 or another parking payment system orsoftware, the meter device connects to parking system's paymentplatforms to receive and collect parking payments from the users,visualizes and estimates available parking spaces that will accommodatea vehicle based on its size, provides information about how long a carhas been parked after parking expiration, helps turn over parkingspaces, tracks parking patterns, counts and monitors every car thatparks in a parking space, provides information about how long a car hasbeen parked after parking expiration, and informs and alerts parkingregulators, personnel and enforcers when vehicles are parked in animpermissible parking zone, parked beyond the permissible parking time,and/or whether free or metered. Both the vehicle users and parkingenforcers benefit from these alerts. The meter device provides parkingsystem users with parking information to pay for parking on the systemplatforms. For example, the meter device will provide and/or transmitinformation such as an area's parking zone identification code and itspermissible parking allotment of time. The meter device will connect toparking system payment platforms to receive and collect parking paymentsfrom their users. Power source 16 may be a rechargeable battery or otherpower source.

The iPEP system may include iPEP-HD 20, as shown in FIGS. 2a, and 2b .iPEP-HD 20 is a standalone hardware device that provides an iPEP userwith an offline option to pay for metered parking with wireless signalstrength. iPEP-HD 20 allows users to pay for parking from within thevehicle on a separate hardware device. In order to use iPEP-HD 20 a usermust have (or create) an iPEP account. Each iPEP-HD 20 is associatedwith at least one vehicle and its vehicle machine readable code 28.iPEP-HD 20 is connected to the user's personal account. iPEP-HD 20 mayalso be accessed by website or a mobile app, for example, if a userwants to remotely change a payment method or add parking time to iPEP-HD20. Device 20 may be embedded into the vehicle. If the user already hasan iPEP account, iPEP-HD 20 can be activated by adding the device serialidentification code 22 (e.g., a number or barcode) to the user'saccount, choosing the vehicle that the device will be used for and theuser's preferred payment method.

iPEP-HD 20 may be any shape, for example rectangular, having at leastone side 21 with at least one display screen 26 and buttons 27 (or akeyboard) for the user to input information. Display 26 may be atouchscreen. Buttons 27 may include number digits that may be used by auser to input information such as a parking zone identification code ofthe area the user parks a vehicle and/or the amount of time the user'svehicle will be parked in the specified parking zone. Buttons 27 mayalso include arrows, “enter” and “clear,” for example, that may be usedto help the user move around screen 26 and input information. After theuser inputs the relevant vehicle information, display screen 26 maydisplay the “Parking Zone Identification Code,” “Parking Duration,”“Payment Information,” “Barcode,” and/or “Time Remaining.” Additionaldisplay features and options may be added which include a “Current Time”and/or the date on screen 26. Device 20 may have a second side 29 whichmay include a camera 23, a machine-readable code, such as barcode 28,device 20 serial identification code 22, and/or an additional display25. Camera lens 23 may be used to take a picture and/or scan images toobtain parking related information, for example, a parking zoneidentification code, such as a barcode, on a street sign. iPEP-HD 20 canscan an identification code, such as a barcode, on an on-street sign oruse its camera to take a picture of the parking zone identification codeor other relevant information, and decode the code for the user, forexample, in an image to text conversion, to complete the parkingprocess. Machine-readable code 28 is a personal and/or vehicleidentification code (for example, an alphanumeric code or barcode) thatthe user obtains when device 20 is registered after purchase. iPEP-HD 20may be associated with one or more machine-readable codes 28 if the userhas more than one on their account. If there is more than onemachine-readable code 28 on the user's account, the user will selectwhich code the parking payment will be associated with. Raw data,processed data, extracted information, alerts, and other types of outputmay be transmitted to an external device via a wireless or wiredinterface allowing the iPEP-HD display 26, 25 to mirror with a mobiledevice, for example, over at least one network interface. iPEP-HD 20 mayinteroperate with IOS or Android devices via applications such asCarPlay and Android auto. The display may also include a lighting systemthat changes color to indicate parking information such as the vehicle'sparking and/or payment status, the remaining permitted parking time, theiPEP hardware health (when relevant), network connectivity, or otherrelevant information.

FIG. 3 depicts how multiple iPEP user interfaces automaticallycommunicate and exchange information with each other when located in thesame vicinity. Each user interface of the iPEP system automaticallygeolocates information such as the parking zone and parking meter, basedon wireless geolocation, GPS interface or IP geolocation. Multipledevices 30, 32, 34 form a mesh network 36 via one more wireless or wiredinterfaces. Information between iPEP user interfaces 30, 32, 34 can beexchanged in a peer-to-peer network. These devices 30, 32, 34 may alsoexchange information with geolocation database 38. Geolocation database38 automatically provides stored and real-time information. Thisinformation includes the parking zone, on-street parking, off-streetparking such as a parking garage and/or parking duration. Thisinformation is gathered and shared via GPS interface, cloud geolocationdatabase, IP geolocation or changes to geolocation coordinates overtime. Independent parking payment applications or parking enforcementapplications may connect with each user interface on the iPEP system.

Parking Payment Process

To pay for parking for a specific vehicle, the vehicle must beregistered on the user's account. Users add their preferred paymentmethod, for example, credit card, to their accounts. They can select topay for the transaction on an individual basis, with prepaid funds addedto their account, and/or on a monthly basis.

Users are able to pay for on-street parking using the iPEP's systempayment platform via the user interface. To complete the parking paymenttransaction, the user provides parking information such as a parkingzone identification code, a parking time duration, the vehicle beingparked, and a selected payment method. To input the parking zoneidentification code the user can enter it manually, scan or take apicture of the code, select it as provided by the system and/or selectthe applicable parking zone identification code on the map. The parkingduration for the vehicle's parking session must be permissible under theparking identification code. If more than one vehicle belongs to theuser's account, the user must specify the applicable vehicle beingparked. After the parking payment transaction is complete, the user'sinterface and homepage will display parking information such as thecurrent active parking session and its duration. The vehicle'smachine-readable code will be activated with the driver's parking statusand provide on-street parking enforcers proof of the user's parkingpayment. The iPEP system will alert the user before a parking session isabout to expire. The user may extend the parking session if availableand permissible under the parking zone.

iPEP users can also pay for off-street parking on the iPEP paymentplatform. The user provides parking information including the parkingvenue, parking duration, vehicle being parked and the payment method.Users can enter the desired parking location, parking time and durationon an iPEP map. The iPEP map will then display available off-streetparking venues and their costs. The user must select one of theavailable parking options displayed. After selecting the displayedparking option, users can reserve and pay for a parking spot in theselected parking venue. After the parking transaction is complete, theuser will receive a machine-readable code, via the user interface, toshow the off-street parking enforcer or entity, such as a parkinggarage, proof of the parking payment and reservation. The vehicle'smachine-readable code will be activated with the driver's parking statusand provide off-street parking enforcers, such as parking garages, proofof the user's parking payment. The user's interface, such as a homepage,will display parking information such as the current parking session andits duration. The iPEP system will alert the user when parking is aboutto expire and allow the user to extend the parking session if availableand permissible by the parking venue. iPEP users can split on-street andoff-street parking payment costs with other participating in-vehicleparkers. Those splitting payment can log into their account or sign inas a guest user.

A user can pay for parking using the iPEP-HD by using the relevantbuttons to input parking information including a parking zoneidentification code of the area the user parks the vehicle and enter thetime duration for the vehicle to be parked in that space.

FIG. 4 is a flow chart that shows the automatic parking payment process(“PPP”). This is a software application that is used in the iPEP system.The PPP may also be used on a standalone basis. PPP allows a user tomake, manage, collect, regulate and track the payment of parking meters,tolls and other charges associated with the vehicle. The PPP alsoincludes software that allows a scanning device to determine whether thevehicle is in compliance with applicable parking regulations. Scanningfunctionality will allow the scanning of barcodes or othermachine-readable codes. PPP also enables the user to select applicableparking zone identification codes or similar designations eitherautomatically or as an option to select by the user when inputtinginformation into the user interface of the iPEP system.

The PPP is shown in FIG. 4. The geolocation coordinates of a parkedvehicle are determined at step 40 from a geolocation database query,automatic geolocation with cellular or Wi-Fi triangulation, GPS, manualinput, or other methods. The coordinates are periodically checked by theiPEP system using PPP and confirmed after an interval of time at step42. The time period for checking (e.g., t) for geolocation coordinatesmay be fixed, adjustable according to a pre-determined policy, ordynamically updated depending on external data. The difference betweentwo consecutive geolocations is computed by a cloud server or the iPEPsystem after they are checked at step 44. In one embodiment, a thresholddetector is applied to the computed difference to determine if there isa change at step 46. This threshold may be fixed and pre-determined,dynamically adjusted depending on external data, or two thresholds maybe used for assessing the confidence in coordinate change detection. Ifa change is detected, the departure of the vehicle from that parkinglocation is ascertained, at step 47 and the coordinates are no longerchecked. If a change is not detected, the parking duration is comparedagainst manually entered parking duration at step 48. If the parkingduration is larger than the manually entered time, an alert is generatedat step 49 and sent to the user with a suggestion for extending theparking duration. If the duration is shorter than the entered time, theentire process is repeated from the start.

Parking Enforcement and Violation Payment Collection

The iPEP system also provides functionality for parking enforcement. TheiPEP system enables parking enforcement personnel to access, regulateand monitor parked vehicles. FIG. 5 provides a flow chart of the parkingenforcement and violation payment collection process. The geolocationcoordinates of a parked vehicle are determined at step 50 from ageolocation database query, automatic geolocation with cellular or Wi-Fitriangulation, GPS, manual input, or other methods. The coordinates areperiodically checked by the iPEP system using PPP and confirmed after aninterval of time at step 51. The time period for checking (e.g., t) forgeolocation coordinates may be fixed, adjustable according to apre-determined policy, or dynamically updated depending on externaldata. The difference between two consecutive geolocations is computed bya cloud server or iPEP system after they are checked at step 52. In oneembodiment, a threshold detector is applied to the computed differenceto determine if there is a change at step 53. This threshold may befixed and pre-determined, dynamically adjusted depending on externaldata, or two thresholds may be used for assessing the confidence incoordinate change detection. If a change is detected, the departure ofthe vehicle from that parking location is ascertained at step 54 and thecoordinates are no longer checked at step 55. If a change is notdetected, the parking duration is compared against manually enteredparking duration at step 56. If the parking duration is larger than themanually entered time, alerts are sent to enforcement authorities viatheir enforcement server at step 501. The enforcement servers maygenerate a parking ticket and transmit it to the user of the violatingvehicle at step 502. The notification may be transmitted to the user viaan application, email, SMS, website or the iPEP-HD. A payment gateway504 is provided to the user and the user can provide payment at step 505for the violation which is sent to the enforcement server.

The parking enforcement functionality compares the parking durationcomputed in step 52 with database entries consisting of the parking timelimit to determine if the parking duration has exceeded the parking timelimit eligibility including parking time limit. The computed timeduration is compared against a threshold to determine parking validity.The system then transmits the vehicle's parking data to an authorizedparking enforcement server. The iPEP system can automatically sendalerts of parking violations to parking enforcement authorities orpersonnel, that may be remotely located, via SMS or other digitalchannels for parking expiry. It is not necessary for parking enforcementpersonnel to leave their office. They can be notified at their desk, forexample, via the cloud of violations. iPEP users can then be notified oftickets, etc. on their user interface. The alerts may includeregistration code (e.g., a number), vehicle ownership information and/orrental company information. The user's vehicle machine-readable code mayalso be manually scanned by parking enforcement authority or personnelfor parking enforcement. A parking enforcement authority can also inputa license plate code (e.g., an alphanumeric code) into a handheld deviceconnected to an enforcement cloud server. Once scanned or a licenseplate has been input, parking payment related information is displayedsuch as outstanding parking tickets and past payments. This allows theenforcing authorities to communicate and exchange data with theviolating iPEP users and generate electronic parking violations andpayment information. This communication between the users' iPEPinterfaces and parking enforcement enables parking ticket delivery andtracking, as well as parking ticket payment from the users.

The iPEP system also provides parking information to the parkingenforcer, such as a municipality, including the number of vehiclesparked in a specific zone, parking/payment information as well asstatuses of parked vehicles, and the number of vehicles parked in anoff-street venue. This information can help enforcers discern vehiclesparked in violation of parking rules, track parking patterns andviolations, collect fees for parking violations, and issue violationnotices.

Parking Prediction and Recommendation

FIG. 6 shows a machine learning system of the iPEP system for parkingavailability predictions and recommendations. The machine learningsystem is on a cloud server. Storage system 60 is on a mobile edge orcloud or distributed between the edge and cloud. Storage system 60collects data from several sensor interfaces from the meter devices. Thesensor interfaces include, but are not limited to, GPS 61, auxiliaryinformation 62, such as fire hydrant or local traffic conditions, videofeed 63, such as a single image or video frame from one or more cameras,audio input 64, such as a microphone or traffic noise, proximity sensoryinformation 65 about nearby vehicles or other objects, and crowdsourcedinformation 66. Video feed 63 is used to provide input of featuresincluding identifying the presence or absence of a vehicle; identifyingempty space between parking lines, markings or similar demarcations suchas a fire hydrant, obstructions, or other parking hinderances; ormeasuring distance between vehicles. Audio input 64 provides input offeatures used to identify local road conditions, for example. Video feed63 and audio input 64 may be combined and used together to inputfeatures. Proximity sensor information 65 can assist in identifyingempty parking spaces. Crowdsource information collection 66 includespublic, private and governmental parking data.

Machine learning classifier 67 is deployed on the edge nodes, cloud, orhybrid edge-cloud infrastructure. Classifier 67 identifies importantfeatures such as time series patterns, vehicle occupancy patterns,parking zone vacancy patterns and road traffic patterns, from thecollected data. Classifier 67 extracts these features, pre-trainspredictor 68 and recommender models 69, and predicts parkingavailability or recommends parking locations. Classifier model 67 may bedeveloped offline. Classifier 67 may also operate in a model-freereinforcement learning environment whereby it learns and corrects itsdecisions dynamically and in real-time from data and received feedback.The features of the machine learning model may include space, time,audio pitch, audio intensity, background noise intensity,vehicle-specific audio features, computer vision features such asdetected video objects, bounding boxes, and confidence values, proximityfeatures, vehicle exhaust features, and natural language featuresextracted from crowdsourced data.

In the model-based machine learning classifier system 67, a pre-builtmodel for parking is deployed on edge nodes or in the cloud. The modelis periodically updated as new data is collected. Classifier 67 outputspredicted availability of parking in a location and time by comparingthe collected data with the pre-build data model. The output ofclassifier 67 may be binary, parking available or not available; ornon-binary, a probability output associated with the availability orunavailability. Machine learning system 67 combines the results of datacomputations performed by the cloud server processor and communicateswith other user interfaces to detect parking availability informationfor broadcasting alerts. Machine learning system 67 includes a predictor68 and recommender 69. The system is trained on a remote server topreface available parking spaces over time and spatial area. Historicdata is collected to pre-train a machine learning parking availabilitypredictor. The input to this predictor encompasses spatial andtime-related sensory and crowdsourced data as shown in FIG. 6. Historicdata is input to a remote server. This data includes parking dataalerts, image video, microphones, proximity sensors, geolocation,weather data, public service announcements, private garageannouncements, other data sources, days of the week, time and otherdata.

Collected data may be filtered to remove anomalies, estimate missingvalues, denoise, interpolate, and undergo other operations to preparefor machine learning model building. Crowdsourced data may also befiltered considering the reliability, reputation, and other behavioraland personal attributes of the data contributor.

Once trained, predictor 68 sends alerts based on prediction to the iPEPsystem user interface regarding vehicular information, such as parkingor traffic conditions. Predictor 68 takes inputs from the users forcontinual training of the machine learning predictor 68. Historical dataand the user input, such as crowdsource data, are used to compute theconfidence probability for prediction.

Machine learning parking availability predictor 68 may consist ofseveral sub-predictors. Each sub-predictor may predict individualfeatures or attributes of the data input. A meta predictor combines theoutputs from each of the sub-predictors for a final prediction. Thishierarchical predictor system updates itself periodically in fixed timeintervals or as sufficient new data is collected. Feedback from theusers, such as to upvote or downvote, on the predicted output, theautomatic computation of prediction errors, and feedback from parkinggarages or public parking may be used as signals to update the parkingavailability models and predictions.

The iPEP system also provides parking recommender 69 recommendingparking locations to users based on their past behavior, personalrequirements, cost, or other attributes. Recommender 69 takes thepredicted parking availability matrix of the machine learning predictor68 as an input and automatically ranks the order from the most to leastrecommended for an individual user. The ranking is based on severalmetrics. These metrics may include the user's profile, shortest distanceto parking location, safest, cheapest, hours of operation, or otherattributes. External data such as discounts, coupons, promotions fromlocal businesses, and/or other factors may also be used to influence theranking and parking recommender 69. Recommender 69 continually learnsand improves itself with fresh data collection. It will dynamicallyupdate recommendations with new data and can improve data quality withuser incentives. Both the iPEP prediction and recommendation models maybe used offline. No changes will be noticeable to the user.

Crowdsourcing Data Collection

The iPEP system may include a crowdsourcing data collection process fordata used for parking predictions and recommendations. FIG. 7 shows acrowdsourcing data collection system 76 used for parking prediction andrecommendations. Behavioral data may be collected from individual iPEPusers via mobile applications, iPEP-HD, car software, websites, or otheruser interfaces or from third-party servers or services. Behavioral dataincludes spatial-temporal parking patterns, choices of parking locationsor garages, usage of coupons or promotions, parking duration, andvehicle type. The behavioral data collection may be shared with themachine learning parking predictor or third-party servers. Additionalbehavioral patterns may be collected with feedback from third-partyapplications or services. Data collection frequency may be influenced bythe accuracy of the parking availability predictor and recommender,delivery of advertisements or promotions from third-party servers, orother factors.

Users can also share and update information on what they encounter whenlooking for parking through real-time for other users to see and benefitfrom. Users can submit their reports on their maps via the userinterface or from their homepage, for example, for other users to see ontheir map. Examples of such reports and alerts include street closures,parking machine or parking zone failures, weather conditions (e.g., snowmounts in parking spots), street congestion parking zone meteridentification code not working, new bike lanes, user leaving a spot andreporting availability, active parking enforcers working, accidents,restaurant seating on sidewalks, construction on a block, and hydrantsor driveways. Every additional user on the iPEP system platform willincrease the ease of parking and the value to other users. Users canrespond to messages and reports that relate to themselves, theirlocation and their parking desires.

Incentives and Advertisements

In order to provide incentives for data crowdsourcing, advertisementsmay be displayed, or rewards and/or products offered. The advertisementsmay include discounts, coupons, or free parking. The advertisements maybe paid advertisements. Reward points may be offered for datacontribution. Products or services may be delivered to a parking lot,vehicle or other parking related location.

Information gathered from the iPEP system may be shared with thirdparties. For example, parking behavior, parking location, and/or parkingduration may be shared with auto insurance companies, car rentalcompanies or other third parties. Vehicle type, color, location, andrelated data may be shared with auto related companies or otherenterprises.

The iPEP system maps will display brand advertisements based on a user'slocation and time. The ads are displayed in the user's iPEP map. Thein-map ads allow a user to locate nearby gas stations, restaurants andstores. The map will also show deals and discounts whereby the user canclick on the ads to receive the deal/discount and place orders inadvance, when available. The advertisements may be displayed on the mapas branded pins, zero-speed takeovers or promoted search ads, forexample. Branded pins are dropped in the user's map like a store sign.They will show up in the vicinity that the user seeks to park. They willalso raise company awareness and draw in-route and parking customers totheir stores. Zero-speed takeover ads are displayed to the user as adigital billboard. They pop up when the user comes to a complete stopfor at least 3 seconds, for example, once the vehicle is parked.Promoted search ads are displayed when a user is searching for a movietheatre, restaurant or store.

In the foregoing specification, the invention has been described withreference to specific embodiments thereof. It will, however, be evidentthat various modifications and changes may be made thereto withoutdeparting from the broader spirit and scope of the invention. Thespecification and drawings are, accordingly, to be regarded in anillustrative rather than a restrictive sense.

What is claimed is:
 1. A personal electronic parking system adapted toidentify, track, predict, alert, manage, pay for and collect paymentfor, regulate and enforce on-street and off-street parking, the systemcomprising: a central cloud network adapted to generate and manage userdata and parking data; a user interface adapted to show users parkinginformation relevant to the user; a unique machine-readable code,wherein the code provides identification of a specific vehicle used bythe user; one or more sensors; one or more meter devices adapted toconnect with the central cloud network and the user interface; and aparking payment and enforcement portal.
 2. The system as recited inclaim 1, wherein the user interface is any suitable device, software,interactive modality or other mechanism able to integrate, manipulateand/or operate the personal electronic parking system and allow a userto input information.
 3. The system as recited in claim 1, wherein theone or more sensors include a proximity sensor, antennae, RFID, acamera, a microphone, and/or GPS.
 4. The system as recited in claim 2,wherein the personal electronic parking system hardware device is astandalone hardware device comprising: at least one user display andinterface; a wireless interface; one or more sensors; a power source;and a machine-readable code.
 5. The personal electronic parking systemas recited in claim 1, wherein the parking payment and enforcementportal includes at least one local processing unit with GPU/CPU, amemory, a storage unit, and a wireless interface.
 6. The personalelectronic parking system as recited in claim 1, further comprising amachine learning system comprising a parking predictor model and arecommender model.
 7. The personal electronic parking system as recitedin claim 1, wherein the machine-readable code is a standalone codeattachable to the vehicle or a personal electronic parking systemhardware device.
 8. A method for managing and enforcing personal parkingfor on-street or off-street parking, the method comprising the followingsteps: providing a personal parking payment, payment collection andenforcement ability; and providing parking availability predictions andrecommendations.
 9. The method for managing and enforcing personalparking as recited in claim 8, wherein personal parking payment, paymentcollection and enforcement comprises: a vehicle user registering avehicle with a vehicle user's personal electronic parking systemaccount; selecting a payment method in the vehicle user's account;determining a first set of geolocation coordinates of the vehicle for aparking session; determining a second set of geolocation coordinates ofthe vehicle after a confirmed time; and comparing the first set ofgeolocation coordinates and the second set of geolocation coordinates,wherein if a change is detected between the first set of geolocationcoordinates and the second set of geolocation coordinates, a departureof the vehicle is determined, and the geolocation coordinates are nolonger determined for the parking session; if a change is not detectedbetween the first set of geolocation coordinates and the second set ofgeolocation coordinates, comparing a current parking duration against aninitially entered parking time for the parking session, if the parkingduration is longer than the initially entered parking time, generatingand sending an alert, if the duration is shorter than the initiallyentered time, repeating the process from the start.
 10. The method asrecited in claim 8 wherein the geolocation coordinates are determinedfrom a geolocation database query, automatic geolocation with cellularor Wi-Fi triangulation, GPS or manual input.
 11. The method as recitedin claim 8, wherein the confirmed time is fixed, adjustable according toa predetermined policy, or dynamically updated depending on externaldata.
 12. The method as recited in claim 8 wherein the alert is sent tothe vehicle user warning the vehicle user of an expired parking sessionand suggesting a parking duration extension.
 13. The method as recitedin claim 8, wherein the alert is sent to a parking enforcement authorityvia a parking enforcement's server.
 14. The method as recited in claim13, further comprising parking violation transmission and paymentcollection comprising the following steps: generating a parkingviolation ticket on the parking enforcement's server; transmitting theparking violation ticket to the vehicle user via a message and providingthe vehicle user with a payment gateway; the vehicle user providingpayment via the payment gateway; and the payment gateway transmittingthe payment to the parking enforcement's server.
 15. The method asrecited in claim 14, wherein the message is sent to the user via anapplication, a mobile application, an email, SMS, a vehicle application,a website, personal electronic parking hardware device, or a userinteraction modality.
 16. The method as recited in claim 8, whereinproviding parking availability predictions and recommendations comprisesthe following steps: collecting data from external sensors; storing datain a storage unit, inputting data into a machine classifier; identifyingimportant features from the stored data; extracting the importantfeatures and training a predictor model on the server to predictavailable parking spaces over time and spatial area; train a recommendermodel; once trained, the predictor model providing a predicted parkingavailability matrix; ranking the predicted parking availability matrixusing the recommender model; recommending parking to the personalparking system user based on user metrics and external data;continuously collecting stored data and updating the predictor andrecommender models; and combining the stored data and user input tocompute confidence probability for predictions and recommendations. 17.The method as recited in claim 16, wherein the user metrics include auser's profile, a user's past behavior, distance, safety, cost,operational hours or crowd sourced data.
 18. The method as recited inclaim 16, wherein the external data includes deals, discounts, coupons,local business promotions.
 19. The method as recited in claim 17,wherein the crowd sourced data includes behavioral data from one or morepersonal parking system users including spatial temporal parkingpatterns, choices of parking locations or garages, usage of coupons orpromotions, parking duration or vehicle type.
 20. The method as recitedin claim 19, wherein the behavioral data is collected via a userinterface or from third party servers or services.
 21. The method asrecited in claim 19 further comprising providing incentives for thecrowd sourced data, wherein the incentives include advertisements fordiscounts, reward points or free products.
 22. A machine learning systemfor on-street and off-street parking availability predictions andrecommendations, the system comprising: a cloud network; at least onestorage unit; at least one sensor interface; a predictor model; arecommender model; and a classifier, wherein the classifier collects andextracts data for a parking predictor model and a recommender model. 23.The machine learning system as recited in claim 22, wherein thepredictor model further comprises sub predictors and a meta predictor,the meta predictor combining outputs from each of the sub predictors fora final prediction.
 24. The machine learning system as recited in claim22, wherein the at least one sensor interfaces are GPS, at least one setof auxiliary information, at least one video feed, at least one audioinput, proximity information, or crowd source gathered information. 25.The system as recited in claim 1, wherein the machine-readable codechanges color based on a parking status.
 26. The system as recited inclaim 9, wherein the payment method is split between two or more useraccounts.